Русская версия

Search document title:
Content search 1 (fast):
Content search 2:
ENGLISH DOCS FOR THIS DATE- Crashing Mus Blocks to Finding Them (WCS-65, DEBUG-06) - B790823-1 | Сравнить
- Product Debug Repair List (DEBUG-10) - B790823-2 | Сравнить

RUSSIAN DOCS FOR THIS DATE- Технология Устранения Недостатков (УНП 1П, ЭСТО 37R) - Б790823-1R84 | Сравнить
CONTENTS Crashing MUs, Blocks To Finding Them CRASHING MUs A. OTHER MISUNDERSTOODS B. OVERTS AND WITHHOLDS C. FALSE DATA D. JUSTIFICATIONS E. SERVICE FACSIMILIES CAUTIONS SUMMARY Cохранить документ себе Скачать
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 23 AUGUST 1979
Issue II
HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex
HCO BULLETIN OF 23 AUGUST 1979
Issue I
RemimeoRemimeo
TechWord Clearers
Qual

Cram Officers

C/SesSupervisors
Product Debug Series 10

Estos

Product Debug Repair List

Tech

Ref:

Qual

  • HCO PL 23 Aug 791 Product Debug Series 1, Esto Series 37, DEBUG TECH
Word Clearing Series 65
Product Debug Series 6
  • HCO PL 23 Aug 79 II Product Debug Series 2, Esto Series 38, DEBUG TECH CHECKLIST
  • Crashing MUs, Blocks To Finding Them

  • Product Debug Series
  • Ref: HCOB 17 Jun 79 Crashing Mis-Us: The Key To Completed Cycles Of Action And Products


    HCOB 8 Sep 64 Overts – What lies behind Them?

    The purpose of this list is to repair a messed up Product Debug (as covered in HCO PL 23 Aug 79 I Product Debug Series 1, Esto Series 37 Debug Tech and HCO PL 23 Aug 79 II Product Debug Series 2, Esto Series 38 Debug Tech Checklist).

    HCOB 7 Aug 79 False Data Stripping

    In the event of somebody getting messed up because of faulty debugging, use this list to clean up the BPC and then get the person back to complete the debug actions.

    HCOB 7 Jul 64 Justifications

    This list is done in session by an auditor and is assessed Method 3.

    HCOB 21 Jan 60 Justification

    Preface each line with: “On your Product Debug handling_____.”

    HCOB 5 Sep 78 Anatomy Of A Service Facsimile

    Each reading line is taken to F/N per the instructions.

    HCOB 6 Sep 78II Service Facsimiles And Rock Slams

    Any R/S turned on on this list must be immediately reported to the Ethics Officer.

    HCOB 6 Sep 78 III Routine Three SC-A Full Service Facsimile Handling Updated With NED

    Any such assessment sheet as this must be placed in the person’s pc folder.

    It may occur in Crashing MU finding that no Crashing MU can be found even though it is obvious from the person’s inability to complete a cycle of action or get out a product that a Crashing MU must exist.

    PC’s NAME: ____________________ _____________________DATE: _______________

    It is vital, in attempting to find someone’s Crashing MUs, that one does not abandon the search simply because, on enquiry, the person is unable to come up with anything. It may take skill and hard work to uncover the Crashing MU but it must be found, no matter how arduous the search. The completion of the cycle of action and the accomplishment of the product depend on locating and clearing up the Crashing MU that is getting in the way.

    AUDITOR: _____________________ ______________________ ______________________

    Crashing MUs can be buried. They can be buried by

    SECTION 1

    A) Other MU words

    1A. Did you have an out-list?______________

    B) Overts or withholds

    (Handle per HCOB 11 Apr 77 List Errors Correction Of, section on “Use of L4BRA.”)

    C) False data

    1B. Were you given a wrong item?______________

    D) Justifications

    (Indicate and handle per HCOB 11 Apr 77 List Errors Correction Of and C/S Series 78.)

    E) Service facsimiles.

    1C. Were you given a wrong why?______________

    Any one of A, B. C, D or E above or a combination of these can prevent one from finding the Crashing MU. One handles by

    (Indicate and handle per HCOB 11 Apr 77 List Errors Correction Of and C/S Series 78.)

    a) Clearing up the other MUs

    1D. Were you being debugged on the wrong product?______________

    b) Pulling the overts or withholds

    (Indicate and handle per C/S Series 78.)

    c) Stripping off the false data

    1E. Was the wrong area addressed?______________

    d) Getting off the justifications

    (Indicate and handle per C/S Series 78.)

    e) Handling the service facsimile or sending the person to an auditor to get audited on it.

    1F. Were you assigned a wrong condition?______________

    If the Word Clearer came across the situation where no Crashing MU could be found despite obvious indications that one existed, he would check for each of the above blocks in turn and handle anything there was to handle on each point. After handling one of the above blocks, he would recheck for the Crashing MU and if still not available to be found and cleared, he would proceed to check the next block and so on until the Crashing MU was found and cleared. One would check for the blocks in the sequence given (A-E) and only go so far as necessary to uncover the Crashing MU.

    (Indicate and handle as a wrong item.)

    CRASHING MUs

    SECTION 2

    The full handling of a Crashing MU itself will be found in:

    2A. Did you have an ARC break?______________

    HCOB 17 Jun 79 Crashing Mis-Us: The Key To Completed Cycles Of Action And Products

    (Fly the ARC break.)

    HCOB 18 Jun 79 The Crashing Mis-U Repair List – LC1

    2B. Did you have a problem?______________

    HCOB 16 Jul 79 The “Elusive” Mis-U Or Crashing Mis-U

    (Fly the problem.)

    HCOB 26 Mar 79RA Misunderstood Words And Cycles Of Action – MU Words And No Products

    2C. Did you have a withhold?______________

    HCOB 7 Jul 79 Crashing Mis-U Definition

    (Pull the withhold.)

    A. OTHER MISUNDERSTOODS

    2D. Did you have an overt?______________

    Ref: Word Clearing Series

    (Pull the overt.)

    The person may have MUs and confusions which are obscuring the Crashing MU. In attempting to find the Crashing MU one might have to find and clear these other MUs before the person can locate the Crashing MU which has been buried by these other MUs and which is hanging up the cycle of action or the product.

    2E. Did the person doing the debug miss a withhold?______________

    A Crashing MU is a MU that crashes a subject and crashes a person. It is straight on the subject-line that is giving trouble and is totally blocking the person’s comprehension of the subject. This is not to be confused with other MUs. These would include grammatical MUs, MUs on disrelated subjects or MUs on simple words. A Crashing MU is quite different. It is directly on the subject and it totally blocks the person’s understanding of the subject and stops any cycles of action or products on that line.

    (Pull the withhold.)

    Handling: Other MUs obscuring the Crashing MU are located and cleared using any of Word Clearing Methods 2-9 or a combination of these. One might have to do Method 2 and Method 4 on certain materials, for example, before the Crashing MU can then be located. Method 9 is a very thorough and fruitful method of word clearing materials. By whatever method, the MUs are found and cleared. Any MUs that come up during Crashing MU Finding are immediately cleared. This does not mean, however, that one has found the Crashing MU. One has simply unburdened it.

    2F. Were overts or withholds restimulated but not blown?______________

    B. OVERTS AND WITHHOLDS

    (Pull the overts or withholds.)

    Ref: Academy Class II Materials

    2G. Was there an overt or withhold that was gotten off more than once?______________

    As covered in HCOB 8 Sep 64 Overts, What Lies Behind Them?, overts and withholds can enter in after the person encounters a misunderstood word or symbol on the subject or in the area. Having committed the overt, the person may now be withholding so hard that it can become impossible to get his attention onto the MU word that comes earlier in time and is more basic than the withhold.

    (Indicate it and 2WC E/S to F/N.)

    An example of this would be someone who had broken a machine as a result of trying to operate it over his MU on how it worked. His attention would become so caught up with withholding this overt that he might not be able to confront the area at all, let alone find the underlying Crashing MU.

    2H. Did somebody say you had an overt or withhold when you didn’t?______________

    The person’s withholds on the subject of the area not only prevent him from talking about it sensibly to the person trying to find his Crashing MUs, but also tend to withhold him from the subject itself. He won’t be able to think well on that subject because he is withholding data concerning it. The person might also be frightened of punishment or discipline if he did reveal his overt. Therefore, communication with the Crashing MU finder or the subject, also may block up his memory or his ability to think on the subject and so a Crashing MU can be buried totally out of sight.

    (Indicate it and 2WC E/S to F/N.)

    Handling: The handling of O/Ws would depend on whether or not one was using a meter for the Crashing MU finding.

    2I. Was there some other kind of out-rud?______________

    In metered Crashing MU finding one would ask:

    (Find out what and handle.)

    “Concerning (subject under discussion) is there anything you are withholding?” and if it was reading one would handle per HCOB 11 Aug 78, I, Rudiments, Definitions And Patter. Suppress and False could be used as needed.

    2J. Were you using the debug as an excuse not to produce?______________

    One could also check and handle:

    (Handle as a withhold.)

    “Concerning (subject under discussion) have you committed any overt?”

    2K. Was there some kind of out-ethics?______________

    “Concerning (subject under discussion) has a withhold been missed?”

    (Handle as a withhold.)

    In non-metered Crashing MU finding one could ask the person if he had any overt or withhold concerning the subject under discussion. Very often, if one is in good communication with the person and there is no accusativeness or duress, he will say, “Well, actually, I didn’t want to tell anyone but I lost all the ruddy rods,” or whatever the withhold was. In non-metered asking for overts or withholds one must get the person meter checked immediately afterwards to ensure nothing gets missed. It goes without saying that a person can get very misemotional or blow or get very angry with the Crashing MU finder if you miss a withhold on him. So don’t be surprised if you get a sudden blow-up when you use un-metered overt or withhold questions.

    2L. Did you have counter-intention?______________

    C. FALSE DATA

    (Handle as a withhold.)

    Ref: HCOB/PL 7 Aug 79 FALSE DATA STRIPPING

    2M. Did you have other-intention?______________

    A person who has been given and has accepted false data or false definitions on a subject may become convinced that he “knows” the words when in fact the data and definitions may be entirely false. This may even prevent the misunderstoods from reading on the meter. It can certainly bury a Crashing MU because the person’s certainty that he “knows” the data will prevent him from looking for the Crashing MU which is blocking him from getting products.

    (Handle as a withhold.)

    Handling: One handles false data by stripping it off exactly per HCOB/PL 7 Aug 79 False Data Stripping. This is a procedure which locates the false data and then blows it by recall. It is an extremely effective way of getting off the false data which is blocking the person’s understanding of a subject by giving him a false understanding.

    2N. Was there any invalidation?______________

    D. JUSTIFICATIONS

    (2WC E/S to F/N.)

    Ref: HCOB 21 Jan 60 Justification

    2O. Was there any evaluation?______________

    HCOB 7 Jul 64 Justifications

    (2WC E/S to F/N.)

    A person can have a defense mechanism whereby he justifies having a Crashing MU by giving reasons why it is OK not to understand the subject or area. He explains why he doesn’t have to understand and makes others wrong for trying to set him straight on it. Examples of this would be:

    2P. Were there ignored originations?______________

    “I’m new and haven’t been at it too long.”

    (2WC E/S to F/N.)

    “I have to spend so much time on my post, I don’t have time to learn about it.”

    2Q. Were you protesting?______________

    “Only a professional could really understand this.”

    (Indicate and 2WC E/S to F/N.)

    “No one really knows anything about that subject anyway.”

    2R. Did you have no interest in the action?______________

    “They keep changing the terminology so how could I learn it.”

    (Find out if it’s out-ruds, MUs or past failures and handle.)

    Handling: The handling of justifications is covered in HCOB 7 Aug 79 False Data Stripping which has several questions in the section on locating the false data which are designed to pull off the person’s justifications for failure to understand a subject or inability to turn out professional products in an area. Basically the questions ask for anything that makes it OK not to know a particular subject or not to get results with that subject. When the justifications are located they are blown with recall, just as with false data in general.

    2S. Was there a failed purpose?______________

    If there are no justifications present or if the trouble does not resolve with pulling off justifications, then it will be handled with the next section – service facsimilies – since justifications as used here are really a specialized kind of self-serving service facsimile. Justifications and service facsimiles are actually cousins.

    (2WC E/S to F/N.)

    E. SERVICE FACSIMILIES

    SECTION 3

    Ref: Academy Class IV Materials

    3A. Did you resent the debug actions?______________

    HCOB 5 Sep 78 Anatomy Of A Service Facsimile

    (Find out why and 2WC E/S to F/N putting in any out-ruds. If the debug was unnecessary indicate it and take it E/S to F/N.)

    HCOB 6 Sep 78 II Service Facsimiles And Rock Slams

    3B. Was there no inspection done to determine what to debug?______________

    HCOB 6 Sep 78 III Routine Three SC-A Full Service Facsimile Handling Updated With New Era Dianetics

    (Indicate and 2WC E/S to F/N. Program him to have the inspection done and then a proper debug.)

    A service facsimile is an idea someone uses to make himself right and others wrong. These ideas are held in by engrams. For the purposes of Crashing MU finding, they can be handled by recall.

    3C. Was the inspection misdone in some way?______________

    If you are trying to find someone’s Crashing MU and he has a service facsimile getting in the way, then his efforts will be taken up entirely with trying to make himself right and you and others wrong and you will not be able to get to the Crashing MU. He would even feel made wrong if a Crashing MU was found.

    (Indicate and 2WC E/S to F/N. Program him to have the inspection done properly and then a proper debug.

    One person who was being checked for a Crashing MU in an area in which she was goofing could not even see her goofs, let alone a Crashing MU. Eventually she admitted that she had the idea that she could not be wrong regarding this particular subject. When this was spotted and cleared up the Crashing MU could be located and the whole area straightened out.

    3D. Did you feel the person doing the debug was acting out of revenge?______________

    Handling: If the person is manifesting the symptoms of a service facsimile or if the failure to find a Crashing MU where one obviously must exist is not resolved with A-D above, then the Word Clearer would ask, “Is there some idea you are using which makes you right and others wrong?” and two-way comm with him about it without getting into listing for an item. Usually the person will give up the service facsimile and realize that he has been making himself right and others wrong. He will feel very relieved to have spotted it and will be able to look for and find his Crashing MU. If, however, the service facsimile does not come up on request and two-way comm, then the person should be sent for handling by an auditor on service facsimiles.

    (Quad ruds and overts on the terminal.)

    CAUTIONS

    3E. Did you feel the person doing the debug was just trying to get even with you?______________

    The remedies given in this HCOB must be understood to be remedies for inability to locate the Crashing MU – they are not substitutes for standard application of the tech of finding and clearing Crashing MUs.

    (Quad ruds and overts on the terminal.)

    One would always begin with the standard approach to finding the Crashing MU and, if none was found, only then would one check for and handle each of the blocks given above in the sequence given.

    SECTION 4

    If one found something on any of A-E above, one would handle it and then check again for the Crashing MU. One does not automatically check all of A-E. The sole idea is to handle whatever is burying the Crashing MU and as soon as that has been achieved one returns to Crashing MU finding.

    4A. Didn’t you understand what was being done?______________

    If half way through the False Data Stripping, for example, the person realizes he has had a Crashing MU on, then that’s it. You wouldn’t now continue the False Data Stripping. You would complete the step you were on and then end off.

    (Handle his MUs and questions.)

    The same goes for any of the remedies. As soon as the Crashing MU is found or findable, the purpose of the remedy has been achieved and that would be it.

    4B. Were there word clearing errors?______________

    As it is fatal to miss a withhold on someone, it is very important that any withhold pulling done is thorough and goes to real VGIs whether it is metered or un-metered. Withhold pulling off the meter must be followed by a meter check, whether anything is found or not.

    (Assess and handle a WCCL.)

    Similarly in asking for a service facsimile it is possible to start the person listing and if he gets sick or caves in later one must assume that this has occurred and get the action repaired in session rapidly.

    4C. Was an MU found that was not cleared?______________

    Note: Of course if the person is PTS and dramatizing creating problems, you may not be able to get anywhere at all until he has been run on Clay Table de-PTSing to full EP.

    (Fully clear the MU to F/N.)

    These cautions are not given here to make it look difficult or dangerous to do Crashing MU finding. It is usually very straightforward. However, if one is going to get results every time, he must be aware of the possible errors or barriers that he may run into and should know how to handle them.

    4D. Was the word cleared not really a misunderstood?______________

    SUMMARY

    (Indicate and 2WC E/S to F/N.)

    Sometimes Crashing MU finding draws a blank even though there is plenty of evidence that a Crashing MU exists.

    4E. were you told you had MUs when you didn’t?______________

    Other misunderstoods, overts or withholds, false data, justifications and service facsimiles can bury the Crashing MU.

    (Indicate and 2WC E/S to F/N.)

    If one runs into this situation, one must not abandon the Crashing MU finding as the person will continue to have difficulty and will not get out his products.

    4F. Was your crashing Mis-U finding messed up?______________

    The answer is to handle the blocks that are preventing the Crashing MU from being found and then find and clear the Crashing MU.

    (Assess and handle a Crashing Mis-U Repair List.)

    Then one can get the spectacular results of this miracle tech every time.

    4G. Was the crashing Mis-U found not fully cleared?______________

    L. RON HUBBARD
    Founder

    (Clear it fully to F/N.)

    LRH:gal

    4H. Couldn’t you find the crashing Mis-U?______________

    (Assess and handle the Crashing Mis-U Repair List.)

    4I. Were you told you had a crashing Mis-U when you didn’t?______________

    (Indicate and take E/S to F/N. Do a Crashing Mis-U Repair List if necessary.)

    4J. Was your crashing Mis-U finding misdone?______________

    (Assess and handle a Crashing Mis-U Repair List.)

    4K. Couldn’t complete some cycle of action?______________

    (2WC E/S to F/N. Send to the Word Clearer for handling with Crashing Mis-U tech.)

    SECTION 5

    5A. Was there false data?______________

    (2WC E/S to F/N. Send to the debugger for False Data Stripping on the area.)

    5B. Was your false data handling messed up?______________

    (Assess and handle the False Data Stripping Repair List.)

    5C. Was the “false data” found not really false data?______________

    (Indicate it and have him spot this. Take it E/S to F/N.)

    5D. Was some false data uncovered but not blown?______________

    (Handle the false data to a blow with the False Data Stripping procedure.)

    5E. Did the person doing the debug give you false data?______________

    (Indicate and strip off the false data per HCOB 7 Aug 79 Product Debug Series 8, Esto Series 36 FALSE DATA STRIPPING.)

    5F. Was the true or correct data never found?______________

    (Indicate and 2WC E/S to F/N. Program him to have this handled with False Data Stripping.)

    5G. Did somebody say you had false data when you didn’t?______________

    (Indicate and 2WC E/S to F/N.)

    5H. Had the false data already been handled?______________

    (Indicate and 2WC E/S to F/N.)

    5I. Were you given any verbal data?______________

    (2WC E/S to F/N. Program this to be handled with the “How to Defeat Verbal Tech Checklist.”)

    5J. Are you operating off false or verbal data?______________

    (Indicate and 2WC E/S to F/N. Program this to be handled with False Data Stripping and the “How to Defeat Verbal Tech Checklist.”)

    5K. Have you given others false data?______________

    (Pull as a withhold. Then strip off any false data he has in the area.)

    5L. Have you tolerated false data being given you?______________

    (Pull as a withhold. Then strip off the false data.)

    5M. Have you concluded something without checking it out to obtain the full facts?______________

    (Handle as a withhold. Then strip off any false data he has on the area.)

    5N. Have you failed to do your homework in your subject?______________

    (Handle as a withhold. Then strip off any false data he has in the area.)

    5O. Have you just hoped something was okay and passed it on as okay when you didn’t know?______________

    (Handle as a withhold. Then strip off any false data he has in the area.)

    5P. Have you pretended knowledge and experience you did not have?______________

    (Handle as a withhold.)

    5Q. Have you given false data to get out of something?______________

    (Handle as a withhold.)

    5R. Have you ever lied about anything in this area?______________

    (Handle as a withhold.)

    SECTION 6

    6A. Was your ethics handling messed up?______________

    (Indicate it and 2WC E/S to F/N. If necessary, assess the appropriate correction list to handle the BPC.)

    6B. Were you not handled on your ethics when you should have been?______________

    (Indicate and 2WC E/S to F/N. Program this ethics situation to be handled by the debugger.)

    6C. Were you told you were out-ethics when you weren’t?______________

    (Indicate and 2WC E/S to F/N.)

    6D. Was there some out-ethics situation that was not detected?______________

    (Pull this as a withhold. Then program for handling according to what comes up.)

    SECTION 7

    7A. Were you trying to justify your actions?______________

    (2WC the justifications E/S to F/N. Then check for and pull any O/Ws in the area of the justifications.)

    7B. Were you trying to justify an overt?______________

    (2WC the justifications E/S to F/N. Then pull the overt.)

    7C. Were you trying to lessen an overt?______________

    (2WC this E/S to F/N. Pull the overt.)

    7D. Is there something that makes it ok for you not to get your product out?______________

    (Have him tell you about it E/S to F/N. Then strip off the justification per HCOB 7 Aug 79 Product Debug Series 8, Esto Series 36 False Data Stripping.)

    7E. Is there some reason why producing an overt product is all right?______________

    (2WC it E/S to F/N. Then strip off the justification per HCOB 7 Aug 79 Product Debug Series 8, Esto Series 36 False Data Stripping.)

    7F. Is there something that makes it ok for you not to be competent on your post?______________

    (2WC it E/S to F/N. Then strip off the justification per HCOB 7 Aug 79 Product Debug Series 8, Esto Series 36 False Data Stripping.)

    SECTION 8

    8A. Is there some idea you were using to make yourself right and others wrong?______________

    (2WC him on this and get him to spot and tell you the service facsimile without getting into listing for it. What you are trying to do is get him to find and blow the service facsimile by recall. If he does not come up with the service facsimile complete the 2WC to F/N and program him for full service facsimile handling.)

    8B. Were you trying to make yourself right and others wrong?______________

    (Handle this as in 8A above.)

    8C. Is there something you are doing to make yourself right?______________

    (Handle as in 8A above.)

    8D. Is there a method of making others wrong?______________

    (Handle as in 8A above.)

    8E. Are you concerned about being right or wrong?______________

    (2WC this E/S to F/N. Program him for full service facsimile handling.)

    8F. Was your service facsimile handling messed up?______________

    (Determine if it is an L&N error or an incomplete list and if so, handle per HCOB 11 Apr 77 List Errors Correction Of and C/S Series 78. Otherwise clean up the BPC with an L1C and program him to have any incomplete handling on service facsimiles completed.)

    SECTION 9

    9A. Was there bad cramming?______________

    (Assess and handle a Cramming Repair List.)

    9B. Were you not crammed when you should have been?______________

    (2WC E/S to F/N. Program him to get the needed cramming done.)

    9C. Was there something else wrong with your cramming?______________

    (Assess and handle a Cramming Repair List.)

    9D. failed to look over the materials of which you had false data or MUs on after you were cleaned up and were still blank on the materials because you hadn’t gone through them again?______________

    (2WC E/S to F/N. Program him to re-cover and restudy the materials and send the Cramming Officer to Ethics.)

    9E. The cramming officer just sympathize with you?______________

    (2WC E/S to F/N. Send the Cramming Officer to Ethics.)

    SECTION 10

    10A. Was there some personnel bug that was not handled. ______________

    (2WC E/S to F/N. Program this to be handled with debug tech.)

    10B. Was there some sort of trouble with personnel that was not found. ______________

    (Indicate and 2WC E/S to F/N. Program for handling according to what comes up.)

    SECTION 11

    11A. Is there some problem with your comm lines. ______________

    (2WC E/S to F/N. Note for further handling with debug tech.)

    11B. No orders. ______________

    (2WC E/S to F/N. Note for handling with debug tech.)

    11C. Cross-orders. ______________

    (2WC E/S to F/N. Note for handling with debug tech.)

    11D. Illegal orders. ______________

    (2WC E/S to F/N. Note for handling with debug tech.)

    11E. Some other trouble with orders. ______________

    (2WC E/S to F/N. Note for handling with debug tech.)

    SECTION 12

    12A. Are you unable to study. ______________

    (2WC E/S to F/N. Program him for the M8 and M9 program and PCRD if necessary.)

    12B. Was there some difficulty with hatting that was not found. ______________

    (2WC E/S to F/N. Program for handling with debug tech.)

    12C. Were you prevented from getting hatted. ______________

    (Indicate and 2WC E/S to F/N. Program for handling with debug tech.)

    12D. Was there some other problem with hatting or study. ______________

    (2WC E/S to F/N. Program for handling with debug tech.)

    12E. Is there no hatting course. ______________

    (2WC E/S to F/N. See that a hatting course is established and that he studies meanwhile.)

    12F. Are there no hats. ______________

    (2WC E/S to F/N. Program him to compile his A-I Hat.)

    SECTION 13

    13A. Was your product clearing messed up. ______________

    (Assess and handle a Product Clearing Correction List.)

    13B. Was your product invalidated. ______________

    (2WC E/S to F/N.)

    13C. Didn’t you know what your product was. ______________

    (2WC E/S to F/N. Program for Product Clearing.)

    13D. Was product clearing not done. ______________

    (2WC E/S to F/N. Program for Product Clearing.)

    SECTION 14

    14A. Was your clay table pts handling messed up. ______________

    (Assess and handle the PTS Clay Table Repair List.)

    14B. Are you connected to someone who is antagonistic to you. ______________

    (2WC E/S to F/N. Send him to get routine PTS handling and program him for PTS Clay Table Handling.)

    14C. Are you connected to someone or something that is suppressive to you. ______________

    (2WC E/S to F/N. Send him to get routine PTS handling and program him for PTS Clay Table Handling.)

    14D. Did someone say you were pts when you weren’t. ______________

    (Indicate and 2WC E/S to F/N.)

    14E. Accidents. ______________

    (2WC E/S to F/N. Send him to get routine PTS handling and program him for PTS Clay Table Handling.)

    14F. Are there lots of problems in your area. ______________

    (2WC E/S to F/N. Program him and any other PTS personnel in his area for PTS handling including Clay Table De-PTSing.)

    SECTION 15

    15A. Was there some exterior influence that was not handled. ______________

    (2WC E/S to F/N. Program for handling with debug tech.)

    15B. Is there something stopping your production which is out of your control. ______________

    (2WC E/S to F/N. Program for handling with debug tech.)

    SECTION 16

    16A. Was there some sort of organizational problem. ______________

    (2WC E/S to F/N. Program for handling with debug tech.)

    16B. Was there some organizational trouble that was not located. ______________

    (2WC E/S to F/N. Program for handling with debug tech.)

    SECTION 17

    17A. Were there false reads. ______________

    (Indicate and take E/S to F/N.)

    17B. Were there missed reads. ______________

    (Indicate and take E/S to F/N. Program him to get what was missed handled with debug tech.)

    17C. Were you handled on something that didn’t need handling. ______________

    (Get what and indicate the unnecessary action. Take it E/S to F/N.)

    17D. Was there something which should have been taken up that wasn’t. ______________

    (2WC E/S to F/N. Program for handling with debug tech.)

    17E. Was something quickied. ______________

    (Indicate and 2WC E/S to F/N. Note for handling with debug tech.)

    17F. Was something left incomplete. ______________

    (2WC E/S to F/N. Program this to be completed per debug tech.)

    17G. Was some part of the debug overrun. ______________

    (Indicate and rehab to F/N.)

    17H. Was something missed. ______________

    (Find out what and 2WC E/S to F/N. Pull any M/W/Hs.)

    SECTION 18

    18A. Was some part of the debug unnecessary. ______________

    (Indicate and 2WC E/S to F/N.)

    18B. Were you not having any trouble getting out your products in the first place. ______________

    (If this is actually the case indicate to him that trying to debug his products when he was already getting them out was an unnecessary action. If necessary take it E/S to F/N.)

    18C. Were your products actually being gotten out. ______________

    (If this is actually the case indicate to him that trying to debug his products when he was already getting them out was an unnecessary action. If necessary take it E/S to F/N.)

    SECTION 19

    19A. Was there something else wrong. ______________

    (Find out what and handle with the appropriate correction list.)

    19B. Were you in some sort of case trouble. ______________

    (Assess and handle a C/S 53.)

    L. RON HUBBARD
    Founder
    LRH:gal